Team member transfer tool

ABSTRACT

The present technology can provide a mechanism for providing a team member transfer interface to an administrator user for transferring team member user accounts from one team to another and also a mechanism for transferring the team member user accounts, such as by switching an assignment of one or more user accounts from a first team to another in a single atomic action. The transferring of the team member user accounts may also depend on passing a set of validation checks that check for inconsistencies that could cause an error in the transfer, and also updating access and privileges associated with being members of certain teams.

TECHNICAL FIELD

The present technology pertains to transferring team member useraccounts by an administrator user having administrator rights, and morespecifically, by transferring team member user accounts without anintermediate state.

BACKGROUND

Team management for a content management system may allow privileges fora set of content items to be extended to user accounts associated with aparticular team. At one time or another, one or more user accounts mayneed to change teams, which can be from one team to another under thesame corporate or organization account or to another corporate ororganization account but under the same content management system.

In some cases, transferring user accounts from one team to another mayrequire the transferring user account to leave its original or sourceteam and revert into a personal account before the user account can beadded to the destination team. This is not favorable for user accountsunder corporate or enterprise accounts, given this may inevitably forcethe user account to break certain obligations under its terms ofservices agreement and/or employment contract for a period of time.

In other cases, the transferring user accounts may be required to remainin an intermediate state for a period of time before being added to thedestination team, where the user accounts do not belong to any team.This may cause errors, such as failing to be transferred to thedestination team properly, if there is a shortage of a number oflicenses available to join the team, for example.

Nonetheless, in all these cases, the issue lies in that the one or moretransferring user accounts fail to migrate directly from one team toanother in a seamless fashion. Moreover, there is no means for anadministrator to initiate a transfer of one or more user accounts fromone team to another.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an example content management system, in accordancewith some embodiments of the present technology;

FIG. 1B illustrates an example configuration of teams servicecontrolling aspects of the client application, in accordance with someembodiments of the present technology;

FIG. 2A illustrates a schematic for an example timeline of a team membertransfer process, in accordance with some embodiments of the presenttechnology;

FIG. 2B illustrates a flowchart of the team member transfer process, inaccordance with some embodiments of the present technology;

FIG. 3A illustrates an example graphical user interface of a managementinterface, in accordance with some embodiments of the presenttechnology;

FIG. 3B illustrates an example graphical user interface of a team membertransfer interface, in accordance with some embodiments of the presenttechnology;

FIG. 3C illustrates an example graphical user interface of a team membertransfer interface, in accordance with some embodiments of the presenttechnology;

FIG. 3D illustrates an example graphical user interface of a team membertransfer interface, in accordance with some embodiments of the presenttechnology;

FIG. 3E illustrates an example graphical user interface of a team membertransfer interface, in accordance with some embodiments of the presenttechnology;

FIG. 3F illustrates an example graphical user interface of a team membertransfer interface displaying an informational prompt, in accordancewith some embodiments of the present technology;

FIG. 4A illustrates examples of different schematics for notificationand progress reports with respect to a status of completion intervalsfor the transfer of team member user accounts, in accordance with someembodiments of the present technology;

FIG. 4B illustrates an example of notification and progress reportingwith respect to the transfer of the team member user accounts, inaccordance with some embodiments of the present technology;

FIG. 4C illustrates an example of notification and progress reportingwith respect to the transfer of the team member user accounts, inaccordance with some embodiments of the present technology;

FIG. 4D illustrates an example of notification and progress reportingwith respect to the transfer of the team member user accounts, inaccordance with some embodiments of the present technology;

FIG. 5A illustrates a flowchart of an example method for transferringteam member user accounts from one team to another, in accordance withsome embodiments of the present technology;

FIG. 5B illustrates a flowchart of another example method fortransferring team member user accounts from one team to another, inaccordance with some embodiments of the present technology; and

FIG. 6 shows an example of a system for implementing various aspects ofthe present technology.

DETAILED DESCRIPTION

Various examples of the present technology are discussed in detailbelow. While specific implementations are discussed, it should beunderstood that this is done for illustration purposes only. A personskilled in the relevant art will recognize that other components andconfigurations may be used without parting from the spirit and scope ofthe present technology.

Content management systems having an organization or corporate accountmay comprise teams that manage and group different user accounts basedon different functions and roles. However, when user accounts need to bemoved from one team to another, transitioning user accounts has remainedflawed with both technical and operational obstacles.

To illustrate, a user account that has corporate/enterprise accountprivileges with respect to a first team may need to return to a personaluser account when it is off-boarded from the first team before it can beon-boarded to another team. In doing so, the user may be unintentionallyviolating terms of employment, by breaching intellectual propertyclauses and/or inadvertently conducting data theft (company data wouldbe transferred to a personal account outside the company's control).Another way of off-boarding may require the user account to becompletely disabled and recreated from scratch on the other team, whichmay result in loss of data. Furthermore, because off-boarding andon-boarding have traditionally been two separate steps, the user accountmust reside in an intermediate state (or be deleted) and by doing so,errors with respect to the transfer could arise. For example, when theuser account has been off-boarded but prior to being on-boarded toanother team, and the number of slots of available members is taken upby another user account, the user account may then be stuck in theintermediate state and there may be a failure to complete the transfer.

The shortage of number of slots may be based on a shortage of licences.With respect to licenses, each member of a team may take up a licenseassociated with the team for team member user accounts. Therefore, whena user account leaves the team, the license previously provided to thatuser account is freed up such that when another user account joins theteam, that license is available for the incoming user account and cannotbe transferred to the destination team.

The disclosed technology addresses the need in the art for a team membertransfer interface and service, such as for a content management system,that provides a technical solution to the technical problems above aswell as others. The team member transfer service may be configured toprovide a team member transfer interface to an administrator user aswell as provide a mechanism for transferring one or more team memberuser accounts, such as by switching an assignment of one or more teammember user accounts from a first team to another team, such as in asingle atomic action. As is described in further detail below, the teammember transfer service enables a transfer of the one or more teammember user accounts from a first team to another without the need of anintermediate state such that the transfer progresses in a more seamlessmanner. As a result, the transferring of access and privileges of thosetransferring team member user accounts is also more seamless andefficient.

Content Management System

In some embodiments the disclosed technology is deployed in the contextof a content management system having content item synchronizationcapabilities and collaboration features, among others. An example systemconfiguration 100 is shown in FIG. 1A, which depicts content managementsystem 110 interacting with client device 150.

Accounts

Content management system 110 can store content items in associationwith accounts, as well as perform a variety of content item managementtasks, such as retrieve, modify, browse, and/or share the contentitem(s). Furthermore, content management system 110 can enable anaccount to access content item(s) from multiple client devices.

Content management system 110 supports a plurality of accounts. Anentity (user, group of users, team, company, etc.) can create an accountwith content management system, and account details can be stored inaccount database 140. Account database 140 can store profile informationfor registered entities. In some cases, profile information forregistered entities includes a username and/or email address. Accountdatabase 140 can include account management information, such as accounttype (e.g. various tiers of free or paid accounts), storage spaceallocated, storage space used, client devices 150 having a registeredcontent management client application 152 resident thereon, securitysettings, personal configuration settings, etc.

Account database 140 can store groups of accounts associated with anentity. Groups can have permissions based on group policies and/oraccess control lists, and members of the groups can inherit thepermissions. For example, a marketing group can have access to one setof content items while an engineering group can have access to anotherset of content items. An administrator group can modify groups, modifyuser accounts, etc.

Content Item Storage

A feature of content management system 110 is the storage of contentitems, which can be stored in content storage 142. Content items can beany digital data such as documents, collaboration content items, textfiles, audio files, image files, video files, webpages, executablefiles, binary files, etc. A content item can also include collections orother mechanisms for grouping content items together with differentbehaviors, such as folders, zip files, playlists, albums, etc. Acollection can refer to a folder, or a plurality of content items thatare related or grouped by a common attribute. In some embodiments,content storage 142 is combined with other types of storage or databasesto handle specific functions. Content storage 142 can store contentitems, while metadata regarding the content items can be stored inmetadata database 146. Likewise, data regarding where a content item isstored in content storage 142 can be stored in content directory 144.Additionally, data regarding changes, access, etc. can be stored inserver file journal 148. Each of the various storages/databases such ascontent storage 142, content directory 144, server file journal 148, andmetadata database 146 can be comprised of more than one such storage ordatabase and can be distributed over many devices and locations. Otherconfigurations are also possible. For example, data from content storage142, content directory 144, server file journal 148, and/or metadatadatabase 146 may be combined into one or more content storages ordatabases or further segmented into additional content storages ordatabases. Thus, content management system 110 may include more or lessstorages and/or databases than shown in FIG. 1A.

In some embodiments, content storage 142 is associated with at least onecontent storage service 116, which includes software or other processorexecutable instructions for managing the storage of content itemsincluding, but not limited to, receiving content items for storage,preparing content items for storage, selecting a storage location forthe content item, retrieving content items from storage, etc. In someembodiments, content storage service 116 can divide a content item intosmaller chunks for storage at content storage 142. The location of eachchunk making up a content item can be recorded in content directory 144.Content directory 144 can include a content entry for each content itemstored in content storage 142. The content entry can be associated witha unique ID, which identifies a content item.

In some embodiments, the unique ID, which identifies a content item incontent directory 144, can be derived from a deterministic hashfunction. This method of deriving a unique ID for a content item canensure that content item duplicates are recognized as such since thedeterministic hash function will output the same identifier for everycopy of the same content item, but will output a different identifierfor a different content item. Using this methodology, content storageservice 116 can output a unique ID for each content item.

Content storage service 116 can also designate or record a content pathfor a content item in metadata database 146. The content path caninclude the name of the content item and/or folder hierarchy associatedwith the content item. For example, the content path can include afolder or path of folders in which the content item is stored in a localfile system on a client device. While content items are stored incontent storage 142 in blocks and may not be stored under a tree likedirectory structure, such directory structure is a comfortablenavigation structure for users. Content storage service 116 can defineor record a content path for a content item wherein the “root” node of adirectory structure can be a namespace for each account. Within thenamespace can be a directory structure defined by a user of an accountand/or content storage service 116. Metadata database 146 can store thecontent path for each content item as part of a content entry.

In some embodiments the namespace can include additional namespacesnested in the directory structure as if they are stored within the rootnode. This can occur when an account has access to a shared collection.Shared collections can be assigned their own namespace within contentmanagement system 110. While some shared collections are actually a rootnode for the shared collection, they are located subordinate to theaccount namespace in the directory structure, and can appear as a folderwithin a folder for the account. As addressed above, the directorystructure is merely a comfortable navigation structure for users, butdoes not correlate to storage locations of content items in contentstorage 142.

While the directory structure in which an account views content itemsdoes not correlate to storage locations at content management system110, the directory structure can correlate to storage locations onclient device 150 depending on the file system used by client device150.

As addressed above, a content entry in content directory 144 can alsoinclude the location of each chunk making up a content item. Morespecifically, the content entry can include content pointers thatidentify the location in content storage 142 of the chunks that make upthe content item.

In addition to a content path and content pointer, a content entry incontent directory 144 can also include a user account identifier thatidentifies the user account that has access to the content item and/or agroup identifier that identifies a group with access to the content itemand/or a namespace to which the content entry belongs.

Content storage service 116 can decrease the amount of storage spacerequired by identifying duplicate content items or duplicate blocks thatmake up a content item or versions of a content item. Instead of storingmultiple copies, content storage 142 can store a single copy of thecontent item or block of the content item and content directory 144 caninclude a pointer or other mechanism to link the duplicates to thesingle copy.

Content storage service 116 can also store metadata describing contentitems, content item types, folders, file path, and/or the relationshipof content items to various accounts, collections, or groups in metadatadatabase 146, in association with the unique ID of the content item.

Content storage service 116 can also store a log of data regardingchanges, access, etc. in server file journal 148. Server file journal148 can include the unique ID of the content item and a description ofthe change or access action along with a time stamp or version numberand any other relevant data. Server file journal 148 can also includepointers to blocks affected by the change or content item access.Content storage service can provide the ability to undo operations, byusing a content item version control that tracks changes to contentitems, different versions of content items (including diverging versiontrees), and a change history that can be acquired from the server filejournal 148.

Content Item Synchronization

Another feature of content management system 110 is synchronization ofcontent items with at least one client device 150 (150A, 150B, 150C . .. ). Client device(s) can take different forms and have differentcapabilities. For example, client device 150A is a computing devicehaving a local file system accessible by multiple applications residentthereon. Client device 150B is a computing device wherein content itemsare only accessible to a specific application or by permission given bythe specific application, and the content items are typically storedeither in an application specific space or in the cloud. Client device150C is any client device accessing content management system 110 via aweb browser and accessing content items via a web interface. Whileexample client devices 150A, 150B, and 150C are depicted in form factorssuch as a laptop, mobile device, or web browser, it should be understoodthat the descriptions thereof are not limited to devices of theseexample form factors. For example a mobile device such as client device150B might have a local file system accessible by multiple applicationsresident thereon, or client device 150B might access content managementsystem 110 via a web browser. As such, the form factor should not beconsidered limiting when considering client 150's capabilities. One ormore functions described herein with respect to client device 150 may ormay not be available on every client device depending on the specificcapabilities of the device—the file access model being one suchcapability.

In many embodiments, client devices are associated with an account ofcontent management system 110, but in some embodiments client devicescan access content using shared links and do not require an account.

As noted above, some client devices can access content management system110 using a web browser. However, client devices can also access contentmanagement system 110 using client application 152 stored and running onclient device 150. Client application 152 can include a clientsynchronization service 156.

Client synchronization service 156 can be in communication with serversynchronization service 112 to synchronize changes to content itemsbetween client device 150 and content management system 110.

Client device 150 can synchronize content with content management system110 via client synchronization service 156. The synchronization can beplatform agnostic. That is, content can be synchronized across multipleclient devices of varying type, capabilities, operating systems, etc.Client synchronization service 156 can synchronize any changes (new,deleted, modified, copied, or moved content items) to content items in adesignated location of a file system of client device 150.

Content items can be synchronized from client device 150 to contentmanagement system 110, and vice versa. In embodiments whereinsynchronization is from client device 150 to content management system110, a user can manipulate content items directly from the file systemof client device 150, while client synchronization service 156 canmonitor directory on client device 150 for changes to files within themonitored folders.

When client synchronization service 156 detects a write, move, copy, ordelete of content in a directory that it monitors, clientsynchronization service 156 can synchronize the changes to contentstorage service 116. In some embodiments, client synchronization service156 can perform some functions of content storage service 116 includingfunctions addressed above such as dividing the content item into blocks,hashing the content item to generate a unique identifier, etc. Clientsynchronization service 156 can index content within client storageindex 164 and save the result in storage index 164. Indexing can includestoring paths plus a unique server identifier, and a unique clientidentifier for each content item. In some embodiments, clientsynchronization service 156 learns the unique server identifier fromserver synchronization service 112, and learns the unique clientidentifier from the operating system of client device 150.

Client synchronization service 156 can use storage index 164 tofacilitate the synchronization of at least a portion of the contentwithin client storage with content associated with a user account oncontent management system 110. For example, client synchronizationservice 156 can compare storage index 164 with content management system110 and detect differences between content on client storage and contentassociated with a user account on content management system 110. Clientsynchronization service 156 can then attempt to reconcile differences byuploading, downloading, modifying, and deleting content on clientstorage as appropriate. Content storage service 116 can store thechanged or new block for the content item and update server file journal148, metadata database 146, content directory 144, content storage 142,account database 140, etc. as appropriate.

When synchronizing from content management system 110 to client device150, a mount, modification, addition, deletion, move of a content itemrecorded in server file journal 148 can trigger a notification to besent to client device 150 using notification service 117. When clientdevice 150 is informed of the change a request changes listed in serverfile journal 148 since the last synchronization point known to theclient device. When client device 150 determines that it is out ofsynchronization with content management system 110, clientsynchronization service 156 requests content item blocks including thechanges, and updates its local copy of the changed content items.

In some embodiments, storage index 164 stores tree data structureswherein one tree reflects the latest representation of a directoryaccording to server synchronization service 112, while another treereflects the latest representation of the directory according to clientsynchronization service 156. Client synchronization service can work toensure that the tree structures match by requesting data from serversynchronization service 112 or committing changes on client device 150to content management system 110.

Sometimes client device 150 might not have a network connectionavailable. In this scenario, client synchronization service 156 canmonitor the linked collection for content item changes and queue thosechanges for later synchronization to content management system 110 whena network connection is available. Similarly, a user can manually start,stop, pause, or resume synchronization with content management system110.

Client synchronization service 156 can synchronize all contentassociated with a particular user account on content management system110. Alternatively, client synchronization service 156 can selectivelysynchronize a portion of the content of the total content associatedwith the particular user account on content management system 110.Selectively synchronizing only a portion of the content can preservespace on client device 150 and save bandwidth.

In some embodiments, client synchronization service 156 selectivelystores a portion of the content associated with the particular useraccount and stores placeholder content items in client storage for theremainder portion of the content. For example, client synchronizationservice 156 can store a placeholder content item that has the samefilename, path, extension, metadata, of its respective complete contentitem on content management system 110, but lacking the data of thecomplete content item. The placeholder content item can be a few bytesor less in size while the respective complete content item might besignificantly larger. After client device 150 attempts to access thecontent item, client synchronization service 156 can retrieve the dataof the content item from content management system 110 and provide thecomplete content item to accessing client device 150. This approach canprovide significant space and bandwidth savings while still providingfull access to a user's content on content management system 110.

Collaboration Features

Another feature of content management system 110 is to facilitatecollaboration between users. Collaboration features include content itemsharing, commenting on content items, co-working on content items,instant messaging, providing presence and seen state informationregarding content items, etc.

Sharing

Content management system 110 can manage sharing content via sharingservice 128. Sharing content by providing a link to the content caninclude making the content item accessible from any computing device innetwork communication with content management system 110. However, insome embodiments a link can be associated with access restrictionsenforced by content management system 110 and access control listdatabase 145. Sharing content can also include linking content usingsharing service 128 to share content within content management system110 with at least one additional user account (in addition to theoriginal user account associated with the content item) so that eachuser account has access to the content item. The additional user accountcan gain access to the content by accepting the content, which will thenbe accessible through either web interface service 124 or directly fromwithin the directory structure associated with their account on clientdevice 150. The sharing can be performed in a platform agnostic manner.That is, the content can be shared across multiple client devices 150 ofvarying type, capabilities, operating systems, etc. The content can alsobe shared across varying types of user accounts.

To share a content item within content management system 110 sharingservice 128 can add a user account identifier or multiple user accountidentifiers to a content entry in access control list database 145associated with the content item, thus granting the added user accountaccess to the content item. Sharing service 128 can also remove useraccount identifiers from a content entry to restrict a user account'saccess to the content item. Sharing service 128 can record content itemidentifiers, user account identifiers given access to a content item,and access levels in access control list database 145. For example, insome embodiments, user account identifiers associated with a singlecontent entry can specify different permissions for respective useraccount identifiers with respect to the associated content item.

To share content items outside of content management system 110, sharingservice 128 can generate a custom network address, such as a uniformresource locator (URL), which allows any web browser to access thecontent item or collection in content management system 110 without anyauthentication. To accomplish this, sharing service 128 can includecontent identification data in the generated URL, which can later beused to properly identify and return the requested content item. Forexample, sharing service 128 can include the account identifier and thecontent path or a content item identifying code in the generated URL.Upon selection of the URL, the content identification data included inthe URL can be transmitted to content management system 110, which canuse the received content identification data to identify the appropriatecontent item and return the content item.

In addition to generating the URL, sharing service 128 can also beconfigured to record in access control list database 145 that a URL tothe content item has been created. In some embodiments, the contententry associated with a content item can include a URL flag indicatingwhether a URL to the content item has been created. For example, the URLflag can be a Boolean value initially set to 0 or false to indicate thata URL to the content item has not been created. Sharing service 128 canchange the value of the flag to 1 or true after generating a URL to thecontent item.

In some embodiments, sharing service 128 can associate a set ofpermissions to a URL for a content item. For example, if a user attemptsto access the content item via the URL, sharing service 128 can providea limited set of permissions for the content item. Examples of limitedpermissions include restrictions that the user cannot download thecontent item, save the content item, copy the content item, modify thecontent item, etc. In some embodiments, limited permissions includerestrictions that only permit a content item to be accessed from with aspecified domain, i.e., from within a corporate network domain, or byaccounts associated with a specified domain, e.g., accounts associatedwith a company account (e.g., @acme.com).

In some embodiments, sharing service 128 can also be configured todeactivate a generated URL. For example, each content entry can alsoinclude a URL active flag indicating whether the content should bereturned in response to a request from the generated URL. For example,sharing service 128 can only return a content item requested by agenerated link if the URL active flag is set to 1 or true. Thus, accessto a content item for which a URL has been generated can be easilyrestricted by changing the value of the URL active flag. This allows auser to restrict access to the shared content item without having tomove the content item or delete the generated URL. Likewise, sharingservice 128 can reactivate the URL by again changing the value of theURL active flag to 1 or true. A user can thus easily restore access tothe content item without the need to generate a new URL.

In some embodiments, content management system 110 can designate a URLfor uploading a content item. For example, a first user with a useraccount can request such a URL, provide the URL to a contributing userand the contributing user can upload a content item to the first user'suser account using the URL.

Authorization Service

In some embodiments, content management system 110 includesauthorization service 132. Authorization service 132 ensures that a useraccount attempting to access a namespace has appropriate rights toaccess the namespace. Authorization service 132 can receive a token fromclient application 152 that follows a request to access a namespace andcan return the capabilities permitted to the user account. For useraccounts with multiple levels of access (e.g. a user account with userrights and administrator rights) authorization service 132 can alsorequire explicit privilege escalation to avoid unintentional actions byadministrators.

Presence and Seen State

In some embodiments, content management system can provide informationabout how users with which a content item is shared are interacting orhave interacted with the content item. In some embodiments, contentmanagement system 110 can report that a user with which a content itemis shared is currently viewing the content item. For example, clientcollaboration service 160 can notify notification service 117 whenclient device 150 is accessing the content item. Notification service117 can then notify all client devices of other users having access tothe same content item of the presence of the user of client device 150with respect to the content item.

In some embodiments, content management system 110 can report a historyof user interaction with a shared content item. Collaboration service126 can query data sources such as metadata database 146 and server filejournal 148 to determine that a user has saved the content item, that auser has yet to view the content item, etc., and disseminate this statusinformation using notification service 117 to other users so that theycan know who currently is or has viewed or modified the content item.

Collaboration service 126 can facilitate comments associated withcontent, even if a content item does not natively support commentingfunctionality. Such comments can be stored in metadata database 146.

Collaboration service 126 can originate and transmit notifications forusers. For example, a user can mention another user in a comment andcollaboration service 126 can send a notification to that user that hehas been mentioned in the comment. Various other content item events cantrigger notifications, including deleting a content item, sharing acontent item, etc.

Collaboration service 126 can provide a messaging platform whereby userscan send and receive instant messages, voice calls, emails, etc.

Collaboration Content Items

In some embodiments content management service can also includeCollaborative document service 134 which can provide an interactivecontent item collaboration platform whereby users can simultaneouslycreate collaboration content items, comment in the collaboration contentitems, and manage tasks within the collaboration content items.Collaboration content items can be files that users can create and editusing a collaboration content item editor, and can contain collaborationcontent item elements. Collaboration content item elements may include acollaboration content item identifier, one or more author identifiers,collaboration content item text, collaboration content item attributes,interaction information, comments, sharing users, etc. Collaborationcontent item elements can be stored as database entities, which allowsfor searching and retrieving the collaboration content items. Multipleusers may access, view, edit, and collaborate on collaboration contentitems at the same time or at different times. In some embodiments thiscan be managed by requiring two users access a content item through aweb interface and there they can work on the same copy of the contentitem at the same time.

Collaboration Companion Interface

In some embodiments client collaboration service 160 can provide anative application companion interface for the purpose of displayinginformation relevant to a content item being presented on client device150. In embodiments wherein a content item is accessed by a nativeapplication stored and executed on client device 150, where the contentitem is in a designated location of the file system of client device 150such that the content item is managed by content application 152, thenative application may not provide any native way to display the aboveaddressed collaboration data. In such embodiments, client collaborationservice 160 can detect that a user has opened a content item, and canprovide an overlay with additional information for the content item,such as collaboration data. For example, the additional information caninclude comments for the content item, status of the content item,activity of other users previously or currently viewing the contentitem. Such an overlay can warn a user that changes might be lost becauseanother user is currently editing the content item.

In some embodiments, one or more of the services or storages/databasesdiscussed above can be accessed using public or private applicationprogramming interfaces.

Certain software applications can access content storage 142 via an APIon behalf of a user. For example, a software package such as anapplication running on client device 150, can programmatically make APIcalls directly to content management system 110 when a user providesauthentication credentials, to read, write, create, delete, share, orotherwise manipulate content.

A user can view or manipulate content stored in a user account via a webinterface generated and served by web interface service 124. Forexample, the user can navigate in a web browser to a web addressprovided by content management system 110. Changes or updates to contentin the content storage 142 made through the web interface, such asuploading a new version of a content item, can be propagated back toother client devices associated with the user's account. For example,multiple client devices, each with their own client software, can beassociated with a single account and content items in the account can besynchronized between each of the multiple client devices.

Client device 150 can connect to content management system 110 on behalfof a user. A user can directly interact with client device 150, forexample when client device 150 is a desktop or laptop computer, phone,television, internet-of-things device, etc. Alternatively oradditionally, client device 150 can act on behalf of the user withoutthe user having physical access to client device 150, for example whenclient device 150 is a server.

Some features of client device 150 are enabled by an applicationinstalled on client device 150. In some embodiments, the application caninclude a content management system specific component. For example, thecontent management system specific component can be a stand-aloneapplication 152, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 110 via a third-party application, such as a web browser, thatresides on client device 150 and is configured to communicate withcontent management system 110. In various implementations, theclient-side application 152 can present a graphical user interface (GUI)for a user to interact with content management system 110. For example,the user can interact with the content management system 110 via a filesystem explorer integrated with the file system or via a webpagedisplayed using a web browser application.

In some embodiments, client application 152 can be configured to manageand synchronize content for more than one account of content managementsystem 110. In such embodiments client application 152 can remain loggedinto multiple accounts and provide normal services for the multipleaccounts. In some embodiments, each account can appear as folder in afile system, and all content items within that folder can besynchronized with content management system 110. In some embodiments,client application 152 can include a selector to choose one of themultiple accounts to be the primary account or default account.

While content management system 110 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 100 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible. Further, a service can have more or lessfunctionality, even including functionality described as being withanother service. Moreover, features described herein with respect to anembodiment can be combined with features described with respect toanother embodiment.

While system 100 is presented with specific components, it should beunderstood by one skilled in the art, that the architecturalconfiguration of system 100 is simply one possible configuration andthat other configurations with more or fewer components are possible.

Teams Service

In some embodiments, content management system 110 includes teamsservice 130. Teams service 130 can provide functionality for creatingand managing defined teams of user accounts. Teams can be created for acompany, with sub-teams (e.g., business units, or project teams, etc.),and user accounts assigned to teams and sub-teams, or teams can becreated for any defined group of user accounts. Teams service 130 canprovide a common shared space for the team, private user accountfolders, and access limited shared folders.

FIG. 1B illustrates an example configuration of teams service 130controlling aspects of client application 152, in accordance with someembodiments of the present technology. More specifically, teams service130 may control management interface 133 (see also FIG. 3A) for anadministrator user account to manage collections and content itemswithin a team(s), and can manage team member user accounts that areassociated with the team(s). Teams service 130 may include team membertransfer service 136 which may control team member transfer interface137 (see also FIGS. 3B-3E).

Team member transfer service 136 may be configured to provide functionsuseful in transferring one or more team member user accounts 135 fromthe source team to the destination team (see also FIG. 2A).Alternatively, or in addition to, transferring one or more team memberuser accounts 135, or a part thereof, may be performed by teams service130. Teams service 130 and/or team member transfer service 136 maycommunicate with identity and access management (IAM) service 138 withrespect to changing access and privileges of team member user accountsin accordance with the transfer. In some embodiments, team membertransfer service 136 can be part of IAM service 138.

Identity and Access Management (IAM) Service

IAM service 138 may be a standalone service that owns concepts of users,teams, and groups within the framework of content management system 110.IAM service 138 may provide all or nothing operations to any operationon a user account, a team, or a group, such as creation, deletion,updating, etc. of the identity or access privileges of the respectiveuser account, team, or group. Groups and teams may be distinguishablebased on a difference in definition and function. For example, addinguser accounts to a team may require changes with permissions to accesscontent items and may be associated with licenses, whereas adding useraccounts to groups may be merely a collection of user accounts, such asorganizing team member user accounts of a team may be further intogroups.

Team Member Transfer Service

In some embodiments, content management system 110 includes team membertransfer service 136. Team member transfer service 136 may providefunctionality for transferring team member user accounts 135 from oneteam to another. FIG. 2A illustrates a schematic for an example sequence200A of a team member transfer process, in accordance with someembodiments of the present technology. With respect to the team membertransfer process, a source team may be a first team that team memberuser accounts 135 should be transferred from, and a destination team maybe another team that team member user accounts 135 should be transferredto. In addition, team member user accounts 135 may be one or more teammember user accounts. The destination team may be one or moredestination teams.

Some preliminary steps may take place prior to team member user accounts135 transferring in team member transfer task 209. For example, teammember transfer interface 137 may display a preliminary determination tohelp administrator user account 208 determine that certain criteria arenot met for a successful transfer with respect to selected team memberuser accounts 135 and the destination team. For example, team membertransfer interface 137 may receive (201) one or more selections of teammember user accounts 135 for transfer and a selection of the destinationteam.

Then, teams service 130 may determine (203) or check that criteria aremet before transferring team member user accounts 135. For example, teammember transfer service 136 may check whether enough licenses areavailable at the destination team for all of team member user accounts135 selected for transfer. Another example may be that team membertransfer service 136 may check if administrator user account 208 hasqualifying administrative rights to manage the destination team. Being aqualifying administrator may require that administrator user account 208be a multi-team administrator. Administrative user account 208 mayobtain qualifying administrative rights to manage the destination teambased on a handshake agreement between the source team and thedestination team. The handshake agreement may be a unidirectionalagreement that permits administrator user account 208 to act as anadministrator of the destination team.

Other criteria that may be checked may include: checking thatadministrator user account 208 is not attempting to transfer itself;checking that team member user accounts 135 selected for transfer aretransferring to teams that administrator user account 208 has qualifyingadministrative rights to manage; checking that team member user accounts135 have not been selected to transfer to teams they are already on orto teams that are suspended; preventing team member user accounts 135selected for transfer from transferring if such team member useraccounts 135 are placed on a legal hold (a team member cannot betransferred due to an HR restriction or such team member user accounts135 have been instructed to preserve electronically stored information);and checking any administrator user account 208 being transferred is notthe last administrator on the source team to avoid leaving the sourceteam without an administrator.

Based on the determining (203) of whether the criteria are met, teammember transfer interface 137 may output (205) transfer error warningsto administrator user account 208, where the transfer error warnings mayindicate what errors may occur if the transfer request is initiated fortransfer. See FIGS. 3D-3E and associated disclosure below for moredetail. Team member transfer interface 137 might permit administratoruser account 208 to still initiate the transfer after outputting thetransfer error warnings. Additionally, team member transfer interface137 may display (207) informational prompt 320 (see FIG. 3F, forexample), that provides more information regarding the transfer.

Then, upon receiving (209) the member transfer request, team membertransfer service 136 may initiate team member transfer task 211. In someembodiments, to double-check that nothing has changed between receiving(209) the selection and when an input effective to initiate the transferis received (211), team member transfer service 136 may confirm (213)the identification of selected team member user accounts 135 and of thedestination team and check (215) or double-check the criteria withrespect to the selection. If the criteria are not met, no team memberuser accounts are transferred.

Team member transfer task 211 may include a collection of tasks thatcollectively transfers team member user accounts 135 to the destinationteam. This collection of tasks may be performed as asynchronousprocesses, which may proceed in series using a finite state machine tomove through the steps in a specific order. Team member transfer task211 may take place in the background as an asynchronous collection oftasks and may occur in parallel to other actions at content managementsystem 110, including transfers of other team member user accountsreceived (209) for transfer. However, it will be appreciated by those ofordinary skill in the art that the collection of tasks do not have torun asynchronously.

Once the determination that the criteria are met, team member transferservice 136 or IAM service 138 may place (216) one or more team membertransfer flags on team member user accounts 135, the source team, and/orthe destination team involved in the transfer. One or more team membertransfer flags may be set to both team member user accounts 135 beingtransferred and administrative user account 208 initiating the transfer.The team member transfer flags may protect against several raceconditions. For example, while the team member transfer flag isassociated with the team member user accounts 135, the team membertransfer flag can prevent team member user accounts 135 from beingtransferred or off-boarded from other teams of which they are members,from being transferred to any other teams other than the teams part ofthe pending transfer, or from accepting group invitations from any otherteams outside the pending transfer.

Similarly, when applied to administrator user account 208, the teammember transfer flag can prevent administrator user account 208 fromlosing its administrative privileges for as long as administrator useraccount 208 is flagged. By freezing these user accounts' rights andprivileges, content management system 110 is provided time to completetasks involved in team member transfer task 211, such as tasks to removethe access privileges regarding the source team. Once the tasks involvedin team member transfer task 211 are complete, the one or more teammember transfer flags may be cleared for each of team member useraccounts 135 on a per user account basis. The team member transfer flagfor administrator user account 208 may be removed after the transfer jobif there are multiple transferring team member user accounts 135.

Then, IAM service 138 may transfer (218) each team member user account135 from the source team to the destination team in a single atomicaction. By doing so, IAM service 138 may switch a team assignment (orteam ID) of the team member user account to one associated with thedestination team. In some embodiments, IAM service 138 may stage allrequested changes for multiple team members temporarily in metadatadatabase 146 and associated databases may be locked so adll requestedchanges for the multiple team members may be finalized and committed atonce in atomic actions for each team member of the multiple teammembers. In addition, team member transfer service 136 and/or teamsservice 130 may assist or be in control of the switching of teamassignment. In switching or transferring (218) team assignment of teammember user accounts 135, IAM service 138 may be adding (220A) teammember user accounts 135 to the destination team and removing (220B)team member user accounts from the source team.

Once team member user accounts have been reassigned through the atomicmove, changes to access privileges and other actions resulting from theteam changes in team assignments may be performed. In some embodiments,changing a team to which a user account is assigned does not, by itself,remove or provide access and privileges that come with team membership.

The change in team assignment will result in enrollment andun-enrollment tasks, where enrollment tasks are necessary actions togive team member user account access and privileges that come with teammembership, while un-enrollment tasks result in necessary actions toremove access and privileges. The enrollment and un-enrollment tasks maybe separate asynchronous tasks for changing enrollment in team groups.Adding (220A) team member user accounts 135 to the destination team maycause enrollment (222) of the team member user accounts 135 to certainteam groups associated with the destination team. Removing (220B) teammember user accounts 135 from the source team may cause un-enrollment(224) of the team member user accounts 135 from certain team groupsassociated with the source team.

For example, for each team, when a new team member joins, by default,the new team member may be added to at least a team group that includeseveryone on the team. In addition, the user account may be added to anaccess control list for content items shared among members of the team.Additionally, a team member might have privileges to share contentitems, or have other rights. When the team member is removed from theteam group the user is included in the team membership, and is removedfrom the access control list for content items shared among members ofthe team, and will have privleges removed.

In some embodiments, an administrator can allow a user account to retaina copy of content items from the team in which the user account is beingremoved. However, if the source team does not permit shared folders frombeing shared outside the source team, administrator user account 208 maynot be allowed to override such a decision, and the user will loseaccess to any content items to which the user account has access byvirtue of team membership.

Any content items to which the user account has access through theirpersonal namespace associated with their user account can be retainedafter the user account has transferred teams. The home namspaces mayinclude content items and data associated therewith that are tieddirectly to the user account itself. In the event that transferring theuser account to a new desitination team requires unmounting the useraccount namespace from a current organization directory and mounting itin a new organization directory (such as when a user is being reassignedto a new subsidiary within a larger organization), un-enrollment tasksand enrollment tasks can also include the unmounting and mounting of theuser account namespace.

FIG. 2B shows an example flowchart 200B of the team member transferprocess, in accordance with some embodiments of the present technology.While FIG. 2B shows particular services within content management system110 performing certain steps, the steps are not required to be performedexplicitly by the illustrated services as shown and are merely examplesof how particular services may perform particular steps.

Team member transfer service may receive (209) a member transferrequest, which may have been inputted by administrator user account 208at team member transfer interface 137. After recieving (209) the membertransfer request, team member transfer service 136 may confirm (213) anidentification of at least one team member user account and anidentification of the destination team that was received by team membertransfer service 136.

Team member transfer service 136 may determine (215) that criteria aremet, where the criteria is to determine whether a team member,administrator, source team, destination team, or a combination thereofis eligible to be included in the transfer request. Team member transferservice 136 may add (220A) team member user accounts identified in thetransfer request to the destination team and remove (220B) team memberuser accounts identified in the transfer request from the source team ina single atomic action for each user account. More specifically, accountdatabase 140 includes records of team member user accounts 135 thatassociate user accounts to team membership(s). The membership on a teamby a user account can be changed, overwriting a previous association toa team for the user account with a new association to a new team for theuser account.

Once team member user accounts identified in the transfer request aresuccessfully switched, team member transfer service 136 may report (221)an updated status.

The removing (220B) and adding (220A) of a user account from/to a teammay not, by itself, change access and privileges that come withmembership on a team. Some of these changes in access and privileges areperformed in additional processes. For example, IAM service 138 may add(222) team member user accounts identified in the transfer request toappropriate team groups of the destination team for adding access andprivileges associated with the destination team. Once team member useraccounts identified in the transfer request are successfully added tothe appropriate team groups, team member transfer service 136 may report(223) an updated status. Additionally, IAM service may remove (224) teammember user accounts identified in the transfer request from appropriateteam groups of the source team. Once the team member user accountsidentified in the transfer request are successfully removed from theappropriate team groups, team member transfer service 136 may report(225) an updated status, such as by providing notification data for teammember transfer interface 137 to display.

FIGS. 3B, 3C, 3D, 3E, and 3F illustrate example graphical userinterfaces of team member transfer interface 137 accessible by anadministrator user account.

FIG. 3A illustrates an example graphical user interface of managementinterface 133 for administrator user account 208. Management interface133 can present a list of teams that administrator user account 208manages, stated in “Trusted Teams” page 302. In “Trusted Teams” page,for each team, “Move members” interface element 304 can be engaged tomove members on teams that administrator user account 208 manages.

As shown in FIGS. 3B, 3C, and 3D, team member transfer interface 137 mayprovide various interactive elements, such as text entry fields ordrop-down menus, for transferring selected team member user accounts toanother team. More specifically, team member transfer interface 137 mayprovide for first interactive element 308A for selecting the destinationteam. Certain teams, such as “Greedy Giraffe” shown in FIG. 3B, may bepre-determined to be not available as the destination team. An availableteam, such as “Entrepreneurial Eagle” shown in FIG. 3B may be selectedby administrator user account 208, in accordance with some embodiments.Team member transfer interface 137 may also provide second interactiveelement 309 for selecting which team member from the source team are tobe transferred, as shown in FIG. 3C.

Team member transfer interface 137 may also receive (201) selection ofteam member user accounts 135 from the source team for transfer viathird interface element 310, a text-entry field as shown in FIGS. 3D and3E. Further, team member transfer interface 137 may output (205) errors314, 316, 318, when certain team member user accounts are selected fortransfer but member transfer request is not yet submitted. For example,team member transfer interface 137 may highlight a potential error, suchas via error 314 as shown as a highlighted box in FIG. 3D with respectto team member “Robert H.”, indicating that there is an issue withrespect to that team member. An error with respect to the transfer mayalso be indicated as error messages 316, such as indicating that acertain number of member user accounts have been selected for transferthat surpasses a supportable limit. Another example of outputting (205)errors 314, 316, 318 may include indicating there is an insufficientnumber of licenses available at the destination team. For example, error318 is indicated as highlighting text for the last three users thatwould not have successfully transferred in FIG. 3E. Consequently, threelicences must be added before a successful transfer may occur.

FIG. 3F illustrates an example graphical user interface of team membertransfer interface 137 displaying (207) informational prompt 320, inaccordance with some embodiments of the present technology.Informational prompt 320 may include warnings and instructions thatadministrator user account 208 may need to be aware of with respect tothe transfer.

FIG. 4A illustrates examples of different schematics for notificationand progress reports regarding status of completion intervals 215 fortransferring team member user accounts 135, in accordance with someembodiments of the present technology. While the tasks in the teammember transfer process are being performed, team member user accounts135 and/or administrator user account 208 may be informed of the statusof transfer. The status may be translated into notifications, statusupdates or reports, or other forms of reporting. Status updates orreports may include when team member user accounts 135 have been removedfrom the groups and/or team groups that team member user accounts 135were given access to. For example, the status report may be shown asprogress bar 402, in-page progress 404, separate progress page 406,emails 414, and notifications 408 such as via notification tray 418 asshown in FIG. 4C or as banners 412, 420 as shown in FIGS. 4B and 4D. Theprogress may also indicate what team member user accounts 135 is stillallowed to do and what access and privileges they may still have atcertain points in the transfer. Additionally, success and failures ofcompletion intervals 215 may also be shown as notifications 410, 413.These updates may also be accessible to other administrators privy tosuch information, such as ones that belong to the same enterprise orcorporate account, to provide more insight regarding the movement ofuser accounts.

FIGS. 5A and 5B are flowcharts of example method 500A and 500B fortransferring team member user accounts 135 from one team to another, inaccordance with some embodiments of the present technology. Although theexample methods depict a particular sequence of operations, the sequencemay be altered without departing from the spirit of the presentdisclosure. For example, some operations depicted may be performed inparallel or in a different sequence that does not materially affect thefunction of the methods. In other examples, different components of anexample device or system that implements the methods may performfunctions at substantially the same time or in a specific sequence.

In some embodiments, methods 500A, 500B may include providing (502) teammember transfer interface 137 to an administrator user account of atleast a first team (the source team). Team member transfer interface 137may be effective to initiate the transfer of one or more team memberuser accounts to another team (e.g., a destination team). In someembodiments, the administrator user account may have administrativerights to the first team and the destination team. For example, teammember transfer service 136 may control team member transfer interface137 provided at client application 152.

The method may include receiving (503) an identification of one or moreteam member user accounts and the destination team into team membertransfer interface 137. For example, team member transfer service 136,as illustrated in FIG. 1B, or team member transfer interface 137, asillustrated in FIGS. 3B-3E, may be effective to receive (503) anidentification of one or more team member user accounts and thedestination team which to associate the one or more team member useraccounts via client application 152.

In some embodiments, team member transfer interface 137 may includeinterface element 312 effective to allow the administrator user accountto specify whether one or more team member user accounts should retainaccess to shared content items shared with one or more team member useraccounts after the transfer. The shared content items may be shared withone or more team member user accounts by virtue of being a member of thefirst team.

In some embodiments, the administrator user account may be required tohave administrative rights concerning the destination team to initiatethe transfer, e.g. the administrator user account has administrativerights, at least sufficient to make membership assignments, to both thesource and destination team.

In some embodiments, method 500 may include presenting (504)informational prompt 320 that explains aspects of the transfer of one ormore team member user accounts to the destination team. For example,team member transfer interface 137 may be effective to present (504)informational prompt 320. In some embodiments, method 500 may includereceiving (505) an input effective to initiate the transfer of one ormore team member user accounts to the destination team. For example,team member transfer service 136, as illustrated in FIG. 1B, or teammember transfer interface 137, as illustrated in FIGS. 3B-3E, may beeffective to receive (505) the input effective to initiate the transferof one or more team member user accounts to the destination team.

In some embodiments, the method 500 may include receiving (506), fromadministrator user account, having administrator rights to at least afirst team (or the source team), a request to transfer or one or moreteam member user accounts from the first team to a second team (or thedestination team). For example, team member transfer service 136, asillustrated in FIG. 1B, or team member transfer interface 137, asillustrated in FIGS. 3B-3E, may be effective to receive (506) therequest to transfer one or more team member user accounts from the firstteam to a destination team.

In some embodiments, method 500 may include performing (507) a set ofvalidation checks to check for inconsistences that would cause one ormore errors during the transfer of one or more team member user accountsfrom the first team to the destination team. The set of validationchecks may be preemptive checks performed before the request fortransfer is received or as final checks after the request for transferis received. The set of validation checks may include checking if asufficient number of licenses are available for one or more team memberuser accounts 135 to join the destination team. For example, team membertransfer service 136, as illustrated in FIG. 1B, and/or team membertransfer interface 137, as illustrated in FIGS. 3B-3E, may be effectiveto perform (507) the set of validation checks to check forinconsistencies.

In some embodiments, method 500 may include assigning (509) a transferpending status to one or more team member user accounts, based on adetermination that one or more team member user accounts is allowed tobe transferred from the first team to the destination team. The transferpending status may impose at least one restriction preventing an actionassociated with one or more team member user accounts from beingperformed. For example, team member transfer service 136 or IAM service138, as illustrated in FIG. 1B, and/or team member transfer interface137, as illustrated in FIGS. 3B-3E, may be effective to assign (509) atransfer pending status to one or more team member user accounts.

In some embodiments, the method 500 includes switching (510) anassignment of one or more team member user accounts from the first teamto the destination team. Furthermore, the switching of the assignment ofone or more team member user accounts 135 from the first team to thedestination team may occur in a single atomic action. For example, IAMservice 138, as illustrated in FIG. 2B, may be effective to switch (510)the assignment of one or more team member user accounts 135 from thefirst team to the destination team. Team member transfer service 136and/or team member transfer interface 137 may also be effective toswitch the assignment.

In some embodiments, the method 500 includes, after switching (510) theassignment of one or more team member user accounts 135 from the firstteam to the destination team, updating (511) one or more databases todisassociate one or more team member user accounts 135 from access andprivileges afforded to members of the first team, and to associate oneor more team member user accounts 135 with access and privilegesafforded to members of the destination team. The disassociation of oneor more team member user accounts from access and privileges may resultin restricting access to documents associated with the first team,groups associated with the first team, or applications associated withthe first team. For example, IAM service 138, as illustrated in FIG. 2B,may be effective to update (511) one or more databases to disassociateone or more team member user accounts from access and privilegesafforded to members of the first team, and to associate one or more teammember user accounts with access and privileges afforded to members ofthe destination team.

Also after switching (510) the assignment, the transfer pending statusmay be removed (512) from one or more team member user accounts. Teammember transfer service 136 or IAM service 138, as illustrated in FIG.1B, and/or team member transfer interface 137, as illustrated in FIGS.3B-3E, may be effective to remove (512) the transfer pending status.Additionally, the method may include, providing (514) a transfer statusprogress indicator regarding the progress of the transfer, one or morenotifications reporting status of one or more completion intervals ofthe transfer, and/or a separate progress page showing real-time progressof the transfer. For example, teams service 130, team member transferservice 136, or IAM service 138, as illustrated in FIGS. 1A-2B, may beeffective to provide a transfer status progress indicator regarding theprocess of the transfer.

FIG. 6 shows an example of computing system 600, which can be, forexample, any computing device making up client device 150, contentmanagement system 110, activity feed service 136 or any componentthereof in which the components of the system are in communication witheach other using connection 605. Connection 605 can be a physicalconnection via a bus, or a direct connection into processor 610, such asin a chipset architecture. Connection 605 can also be a virtualconnection, networked connection, or logical connection.

In some embodiments, computing system 600 is a distributed system inwhich the functions described in this disclosure can be distributedwithin a datacenter, multiple datacenters, a peer network, etc. In someembodiments, one or more of the described system components representsmany such components each performing some or all of the function forwhich the component is described. In some embodiments, the componentscan be physical or virtual devices.

Example system 600 includes at least one processing unit (CPU orprocessor) 610 and connection 605 that couples various system componentsincluding system memory 615, such as read only memory (ROM) 620 andrandom access memory (RAM) 625 to processor 610. Computing system 600can include a cache of high-speed memory 612 connected directly with, inclose proximity to, or integrated as part of processor 610.

Processor 610 can include any general purpose processor and a hardwareservice or software service, such as services 632, 634, and 636 storedin storage device 630, configured to control processor 610 as well as aspecial-purpose processor where software instructions are incorporatedinto the actual processor design. Processor 610 may essentially be acompletely self-contained computing system, containing multiple cores orprocessors, a bus, memory controller, cache, etc. A multi-core processormay be symmetric or asymmetric.

To enable user interaction, computing system 600 includes an inputdevice 645, which can represent any number of input mechanisms, such asa microphone for speech, a touch-sensitive screen for gesture orgraphical input, keyboard, mouse, motion input, speech, etc. Computingsystem 600 can also include output device 635, which can be one or moreof a number of output mechanisms known to those of skill in the art. Insome instances, multimodal systems can enable a user to provide multipletypes of input/output to communicate with computing system 600.Computing system 600 can include communications interface 640, which cangenerally govern and manage the user input and system output. There isno restriction on operating on any particular hardware arrangement andtherefore the basic features here may easily be substituted for improvedhardware or firmware arrangements as they are developed.

Storage device 630 can be a non-volatile memory device and can be a harddisk or other types of computer readable media which can store data thatare accessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs), read only memory (ROM), and/or somecombination of these devices.

The storage device 630 can include software services, servers, services,etc., that when the code that defines such software is executed by theprocessor 610, it causes the system to perform a function. In someembodiments, a hardware service that performs a particular function caninclude the software component stored in a computer-readable medium inconnection with the necessary hardware components, such as processor610, connection 605, output device 635, etc., to carry out the function.

For clarity of explanation, in some instances, the present technologymay be presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware services or services, alone or in combination with otherdevices. In some embodiments, a service can be software that resides inmemory of a client device and/or one or more servers of a contentmanagement system and perform one or more functions when a processorexecutes the software associated with the service. In some embodiments,a service is a program or a collection of programs that carry out aspecific function. In some embodiments, a service can be considered aserver. The memory can be a non-transitory computer-readable medium.

In some embodiments, the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer-readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The executable computer instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, solid-state memory devices, flash memory, USB devices providedwith non-volatile memory, networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include servers,laptops, smartphones, small form factor personal computers, personaldigital assistants, and so on. The functionality described herein alsocan be embodied in peripherals or add-in cards. Such functionality canalso be implemented on a circuit board among different chips ordifferent processes executing in a single device, by way of furtherexample.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. A method comprising:receiving, from an administrator user having administrator rights to atleast a first team, a request to transfer one or more team member useraccounts from the first team to a destination team; performing a set ofvalidation checks to check for inconsistences that would cause one ormore errors during a transfer of the one or more team member useraccounts from the first team to the destination team; assigning atransfer pending status to the one or more team member user accounts,the transfer pending status imposing one or more restrictions preventingan action associated with the one or more team member user accounts frombeing performed; switching an assignment of the one or more team memberuser accounts from the first team to the destination team; and removingthe transfer pending status from the one or more team member useraccounts.
 5. The method of claim 4, wherein the set of validation checksinclude checking if sufficient number of licenses are available for theone or more team member user accounts to join the destination team. 6.The method of claim 4, wherein the set of validation checks arepreemptive and performed before an input effective to initiate thetransfer is received, and the administrator user is notified of anypreemptive errors in an team member transfer interface.
 7. The method ofclaim 4, wherein the assigning is based on a determination that the oneor more team member user accounts is allowed to be transferred from thefirst team to the destination team, and wherein the removing thetransfer pending status is after completing the transfer of the one ormore team member user accounts to the destination team.
 8. The method ofclaim 4, further comprising: during the transfer of the one or more teammember user accounts to the destination team, providing at least one of:a transfer status progress indicator regarding a process of thetransfer, one or more notifications reporting status of one or morecompletion intervals of the transfer, and a separate progress pageshowing real-time progress of the transfer.
 9. (canceled)
 10. The methodof claim 4, wherein the switching of the assignment of the one or moreteam member user accounts from the first team to the destination teamoccurs in a single atomic action.
 11. The method of claim 4, furthercomprising: after switching the assignment of the one or more teammember user accounts from the first team to the destination team,updating one or more databases to disassociate the one or more teammember user accounts from access and privileges afforded to members ofthe first team, and to associate the one or more team member useraccounts with access and privileges afforded to members of thedestination team.
 12. The method of claim 11, wherein the disassociationof the one or more team member user accounts from access and privilegesafforded to members of the first team results in restricting access, bythe one or more team member user accounts, to documents associated withthe first team, groups associated with the first team, or applicationsassociated with the first team.
 13. A non-transitory computer-readablemedium comprising: instructions stored therein which, when executed byone or more processors, cause the one or more processors to: receive,from an administrator user having administrator rights to at least afirst team, a request to transfer one or more team member user accountsfrom the first team to a destination team; perform a set of validationchecks to check for inconsistencies that would cause one or more errorsduring the transfer of the one or more team member user accounts fromthe first team to the destination team; assign transfer pending statusto the one or more team member user accounts, the transfer pendingstatus imposing one or more restrictions preventing an action associatedwith the one or more team member user accounts from being performed;switch an assignment of the one or more team member user accounts fromthe first team to the destination team; and remove the transfer pendingstatus from the one or more team member user accounts.
 14. Thenon-transitory computer-readable medium of claim 13, wherein theswitching of the assignment of the one or more team member user accountsfrom the first team to the destination team occurs in a single atomicaction.
 15. The non-transitory computer-readable medium of claim 13,wherein further instruction cause the one or more processors to: provideat least one of: a transfer status progress indicator regarding processof the transfer, one or more notifications reporting status of one ormore completion intervals of the transfer, and a separate progress pageshowing real-time progress of the transfer.
 16. The non-transitorycomputer-readable medium of claim 13, wherein further instruction causethe one or more processors to: notify the administrator user of anypreemptive errors, wherein the set of validation checks are preemptivelychecked before input effective to initiate the transfer is received. 17.The non-transitory computer-readable medium of claim 16, wherein the setof validation checks include checking if sufficient number of licensesare available for the one or more team member user accounts to join thedestination team.
 18. The non-transitory computer-readable medium ofclaim 13, wherein further instruction cause the one or more processorsto: after switching the assignment, update one or more databases todisassociate the one or more team member user accounts from access andprivileges afforded to members of the first team, and to associate theone or more team member user accounts with access and privilegesafforded to members of the destination team.
 19. The non-transitorycomputer-readable medium of claim 18, wherein the disassociation of theone or more team member user accounts from access and privilegesafforded to members of the first team results in restricting access, bythe one or more team member user accounts, to documents associated withthe first team, groups associated with the first team, or applicationsassociated with the first team.
 20. A system comprising: one or moreprocessors; and at least one computer-readable storage medium havingstored therein instructions which, when executed by the one or moreprocessors, cause the system to: receive, from an administrator userhaving administrator rights to at least a first team, a request totransfer one or more team member user accounts from a first team to adestination team; perform a set of validation checks to check forinconsistencies that would cause one or more errors during the transferof the one or more team member user accounts from the first team to thedestination team; assign transfer pending status to the one or more teammember user accounts, the transfer pending status imposing one or morerestrictions preventing an action associated with the one or more teammember user accounts from being performed; switch an assignment of theone or more team member user accounts from the first team to thedestination team; and remove the transfer pending status from the one ormore team member user accounts.
 21. The system of claim 20, wherein theswitching of the assignment of the one or more team member user accountsfrom the first team to the destination team occurs in a single atomicaction.
 22. The method of claim 4, further comprising: provide a teammember transfer interface to the administrator user, the administratoruser having administrator rights concerning at least the first team andthe team member transfer interface being effective to initiate thetransfer of the one or more team member user accounts to the destinationteam; receiving an identification of the one or more team member useraccounts and the destination team in the team member transfer interface;causing presentation of an informational prompt explaining aspects ofthe transfer of the one or more team member user accounts to thedestination team; and receiving an input effective to initiate thetransfer of the one or more team member user accounts to the destinationteam.
 23. The method of claim 22, wherein the team member transferinterface includes an interface element effective to allow theadministrator user to specify whether the one or more team member useraccounts should retain access to shared content items shared with theone or more team member user accounts after the transfer, wherein theshared content items are shared with the one or more team member useraccounts by virtue of being a member of the first team.
 24. The methodof claim 4, wherein the administrator user is required to have theadministrator rights concerning the destination team to initiate thetransfer.